Repository navigation
chore: Bump GitHub Actions to their Node.js 24 versions - #21
Merged
Merged
Conversation
Generated-by: termag
There was a problem hiding this comment.
Risk: medium. Not approved: this exceeds the low-risk threshold because it major-bumps GitHub Actions in CI, including the action that retrieves SDK secrets. Cursor Bugbot and Cursor Security Agent completed with no findings that need human review; human review is needed and no reviewers were assigned.
Sent by Cursor Approval Agent: SDK - Pull Request Router and Approver
kinyoklion
approved these changes
Nov 17, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.


Summary
GitHub has deprecated the Node.js 20 runtime for JavaScript actions, and workflows in this repository print a deprecation warning on every run. This PR bumps each action that runs on Node.js 20 or older to its latest major release, which runs on Node.js 24. Tag pins stay tag pins. SHA pins move to the SHA of the new release, with a version comment.
actions/checkoutv4v7actions/setup-javav4v6launchdarkly/gh-actions/actions/release-secretsrelease-secrets-v1.1.0release-secrets-v1.2.1None of the bumps change the inputs this repository passes.
Behavior changes to know about:
actions/checkoutv6 and later store the persisted credentials in a separate file under$RUNNER_TEMP, not in.git/config.release-secrets-v1.2.1reads SSM parameters with a bundled script in place ofdkershner6/aws-ssm-getparameters-action. Its inputs are the same.Opened from termag
Note
Overview
Updates the build-and-run CI workflow to newer GitHub Actions that run on Node.js 24, removing deprecation warnings from Node 20.
actions/checkoutmoves from v4 to v7,actions/setup-javafrom v4 to v6, andlaunchdarkly/gh-actionsrelease-secrets from v1.1.0 to v1.2.1. Inputs passed to each step are unchanged;verify-hello-appis untouched.Worth noting for reviewers: checkout v6+ stores persisted credentials under
$RUNNER_TEMPinstead of.git/config, and release-secrets v1.2.1 fetches SSM parameters with an internal script rather thanaws-ssm-getparameters-action.Reviewed by Cursor Bugbot for commit 48267c8. Bugbot is set up for automated code reviews on this repo. Configure here.